Skip to main content
Brighton and Hove City Council

Brownfield land

There is a problem

  • GeoX,GeoY column must have valid coordinates

SHLAA0180

SiteReference
SHLAA0180
SiteNameAddress
Sackville Trading Estate/Coal Yard Sackville Road
Deliverable
yes
HazardousSubstances
yes
Hectares
1.77
MinNetDwellings
NetDwellingsRangeFrom
564
NetDwellingsRangeTo
564
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2020-08-06
PermissionType
full-planning-permission
PlanningHistory
https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=Q1OISADM0PA00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=PIYQLIDM0PA00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6EDMXE868|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6VDMXE228
PlanningStatus
permissioned
SiteplanURL
https://new.brighton-hove.gov.uk/sites/default/files/planning_bc_regen/policy/brownfield-sites/shlaa0180-sackville-trading-estate-coal-yard-sackville-road.pdf
GeoX
POINT(-0.176409 50.837807)
GeoY
POINT(-0.176409 50.837807)
Notes
BH2019/03548 Approved Aug 2020 commenced summer 2021. PPA Signed April 2017. Pre App discussions. The previous use of the proposed development site as a railway yard and industrial site presents a high risk of contamination that could be mobilised during construction to pollute controlled waters. The east and south sides of the site has some history of contaminative use and this is referenced in the RSK land contamination report of 4/8/17.
OrganisationLabel
OrganisationURI
LastUpdatedDate
2022-12-05
FirstAddedDate
2017-09-18
EndDate
GeoX,GeoY

Geometry must use WGS84, OSGB or Mercator coordinates

Geometry must use WGS84, OSGB or Mercator coordinates

Geometry must use WGS84, OSGB or Mercator coordinates

How to improve Brighton and Hove City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL